Add new vehicle_label field to vehicles table#250
Conversation
|
Documentation available at: |
|
Should samples/template/TIDES/vehicles.csv also be update to add the field. |
|
Data Validation Report
|
Yes, I went ahead and added |
CTRAN-Sutinen
left a comment
There was a problem hiding this comment.
vehicle_label is functionally a unique id, I think we need to have a uniqueness constraint.
Drive-by note: at least for MBTA this is not the case. We have vehicles with the same label, even inside a single mode. |
Summary
Adds an optional
vehicle_labelfield to thevehiclestable to distinguish between internal vehicle IDs and public-facing vehicle numbers displayed on the exterior if vehicles. This new field aligns with GTFS-realtime VehicleDescriptor which has bothidandlabel.Resolves #240
Changes
spec/vehicles.schema.jsonadded new optional fieldvehicle_label:stringUser-visible label for the vehicle, such as the vehicle number displayed on the exterior. This may differ from vehicle_id, which is the internal identifier. Aligns with GTFS-realtime VehicleDescriptor.label.vehicle_idCHANGELOG.mdadded entry under[Unreleased]>### AddedReason for this change
Agencies often have two different identifiers for vehicles:
vehicle_id) used in fleet management, maintenance systems, and internal databasesvehicle_label) displayed on the vehicle exterior for passengers and customer serviceCurrently the TIDES spec only has
vehicle_id, which forces agencies to either lose the public-facing number or use inconsistent workarounds. Addingvehicle_labelprovides a standard place for this common data element (and aligns with GTFS-realtime'sVehicleDescriptor.label).- See related discussion in Issue #240 and Fall 2025 TIDES Issues Working Group notes from December 10.
Review checklist
Per change management policy, the following must be met before feature branch changes can merge to
developbranch: